Test registry cache - do not merge - #9049

PR Summary

Medium Risk
Switching the reusable workflow from @main to @js-builds-2 changes CI build/deploy for every trigger of this workflow; unintended merge could destabilize or diverge from standard pipelines until reverted.

Overview
What changed

The deploy-pm4 workflow no longer calls the shared deploy-pm4.yml workflow at @main; it now references @js-builds-2, so all runs of this workflow use that branch’s CI behavior (aligned with the PR’s experimental ci:k8s-branch:test-registry-cache intent).

README.md gains a single stray . as the first line before the existing heading—likely accidental noise rather than real documentation.

Review focus

Confirm that pinning to js-builds-2 is intentional and temporary, and whether the README leading . should be dropped before merge.

^{Reviewed by Cursor Bugbot for commit cef3148. Bugbot is set up for automated code reviews on this repo. Configure here.}

QA server K8S was successfully deployed https://ci-df5ad1fe74.engk8s.processmaker.net

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

QA server K8S was successfully deployed https://ci-df5ad1fe74.engk8s.processmaker.net

QA server K8S was successfully deployed https://tenant-1.ci-df5ad1fe74.engk8s.processmaker.net

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube